• Preparing and performing the conversion of your SAP ERP system to a SAP S/4HANA on-premise system (or to SAP S/4HANA Cloud, private edition) using Software Update Manager (SUM) 2.0 SP15 with or without Database Migration Option (DMO) of SUM 2.0 SP15
• Errors during and after this conversion process
• Additional information to the related guides mentioned below

System conversion, SAP S/4HANA, ERP, Software Update Manager, SUM 2.0, upgrade, conversion, DMO, database migration option

This SAP Note applies to the conversion procedure of SAP ERP systems to SAP Business Suite 4 SAP HANA (SAP S/4HANA) using the Software Update Manager.

This is the SAP Note with additional and latest information on the conversion process to S/4HANA using Software Update Manager 2.0 SP15. Since it is updated regularly, read it again immediately before starting the tool!

Contents
Part A: Further SAP Notes and Documentation
Part B: Release restrictions and limitations
Part C: General Information / Problems
           I/.......Important General Information
           II/ .... Corrections to the Guide or Online Help
           III/ ....Preparing the Conversion
           IV/..... Problems During the Conversion Process
           V/ ..... Problems After the Conversion
Part D: Chronological Summary




**************************************
Part A: Tool, Further SAP Notes and Documentation

SUM Tool:

Before you start the conversion, make sure that you have the latest available version of the Software Update Manager. Only this version contains the latest corrections and is updated regularly. See SAP Help Portal at https://support.sap.com/sltoolset -> tab "System Maintenance" -> "System Conversion to SAP S/4HANA using SUM 2.0".

Before you start using the SUM tool, make sure that you have the latest version of the corresponding guides:

• Guide for Conversion with SUM: Conversion to SAP S/4HANA using SUM 2.0 SP15: ABAP Systems on <operating system>
• SUM 2.0 Guide: Updating SAP ABAP Systems on <operating system>: <source database>
• DMO Guide: Database Migration Option of SUM 2.0 SP15 for Target Database SAP HANA

The guides are available on the SAP Help Portal at: https://support.sap.com/sltoolset -> tab "System Maintenance". Please bear in mind:

• The DMO guide is a supplement to the SUM Guide.
• The Conversion with SUM Guide is a reduced version of both the SUM Guide and the DMO Guide.

See also the S/4HANA Conversion Guide as well as other S/4HANA documentation available on the SAP Help Portal at http://help.sap.com/s4hana -> <your on-premise version>.

If you want to use the approach "Downtime-Optimized Conversion to SAP S/4HANA", see SAP Note 3211805 or in the SAP Support Portal the page about Downtime-Optimized Conversion.

SAP Notes:

See also the latest versions of the following SAP Notes:

• Additional information regarding the SUM scenarios: Conversion, DMO:

Central Note - Software Update Manager 2.0 SP15....................................... 3146834
Database Migration Option (DMO) of SUM 2.0 SP15....................................... 3206747
Downtime-Optimized Conversion with SUM 2.0 SP15....................................... 3211805

• Additional information regarding the source databases:

SAP MaxDB ............................................................................ 3107171
IBM Db2 for Linux, UNIX and Windows .................................................. 3227542
IBM Db2 for z/OS ..................................................................... 3064244
MS SQL Server ........................................................................ 2977565
Oracle ............................................................................... 2976852
SAP ASE............................................................................... 3109489
SAP HANA DB........................................................................... 3206676
IBM Db2 for i ........................................................................ 3113353

• Additional information regarding the source operating system:

IBM i ................................................................................ 3113353

• Release information concerning target SAP S/4HANA or SAP BW4/HANA (contains also further information in terms of conversion and restrictions)

SAP S/4HANA 1909: Release Information Note............................................ 2769531
SAP S/4HANA 2020: Release Information Note............................................ 2884313
SAP S/4HANA 2021: Release Information Note............................................ 3015539

SAP BW4/HANA: Release Information/Restrictions Note for SAP BW/4HANA 2.0.............. 2733740

 

Part B: Release restrictions and limitations

-------------------< Update D029945 SEP/28/20 >----------------------
Supported start releases
For more details and a graphical representation of the transition paths, see the PDF document that is attached to this SAP Note.
For detailed information on equivalence level and support package stack, see SAP Notes mentioned above.

Part C: General Information / Problems

I/ Important General Information

--------------------< Update D023536 FEB/03/21 >-----------------------
-----------------------< D031330 AUG/08/16 >--------------------------
SUM creates shadow repository on target database
The shadow system is one way to reduce the downtime during a system maintenance. It consists of a shadow instance and a shadow repository, and it is already created and exists during uptime processing of SUM. As a consequence, the downtime is reduced. For all migration scenarios, the Software Update Manager creates the shadow repository on the target database. This applies also for a system conversion to SAP S/4HANA including a database migration to SAP HANA database. Note again that only database migration scenarios are concerned. This is the case, when your source system is not based on SAP HANA database.
For more information, see in the SAP community the blog https://blogs.sap.com/?p=864845.


-----------------------< D031330 APR/28/16 >--------------------------
DVDs not required anymore, archives are calculated automatically
The DVDs that are formerly required for upgrade scenarios (export DVD, language DVD, or kernel DVD) are not needed anymore. The Maintenance Planner calculates all necessary archives for the stack.xml file automatically. Note that you have to select the appropriate kernel archives including the related files such as IGSEXE.SAR manually in the Maintenance Planner.




II/ Corrections to the Guide or Online Help



./.



III/ Preparing the Conversion

----------------< D023536 08/FEB/22 >---------------------------------
S/4HANA 2021: Tasks cannot be released during SPDD
The tasks of the modification transport cannot be released during SPDD because the manual activation of ABAP Dictionary objects is no longer allowed in the shadow instance. As a result, the SPDD transport cannot be marked at this time. However, since the objects that are modified during SPDD are nevertheless correctly transferred to the working set of the activation phase, you do not need to release the tasks at this point in time. Release the tasks and transport after the conversion is complete.

-------------------< Update D044220 15/NOV/2022 >-----------------------
-----------------------< D033068 29/MAR/2021 >--------------------------
Target S/4HANA 2020 or higher on Linux: Consider supported SLES and RHEL versions
If you want to update or upgrade your SAP S/4HANA system to version 2020 or higher, make sure that the application server is running on one of the following operating systems

• SUSE Linux Enterprise Server (SLES)
• Red Hat Enterprise Linux (RHEL) for SAP Solutions
• Red Hat Enterprise Linux (RHEL) for SAP Applications

that also supports SAP kernel 789 or higher. The reason for this is that the LOADTOOLS of SUM require an environment in which SAP kernel 789 or higher is running. Otherwise, error messages such as the following can occur:

"/lib64/libstdc++.so.6: Version `GLIBCXX_3.4.26' not found (required by .../SUM/abap/bin_s4/SAPuptool)".

Note:

• See also SAP Note 3119751 for requirements regarding SAP Kernel 788 or higher.
• The versions SLES 12 or RHEL 7 are no longer supported.
• If the SAP_BASIS target system is 753 or higher and your application server is based on Windows, consider SAP Note 2734697.
  
  

----------------------< D039661 SEP/17/2019 >-------------------------
Oracle on SAP system with MSCS Cluster: Check DB/OS combination for conversion to SAP S/4HANA 1909
You have an SAP system running on Windows operatings system with Microsoft Cluster Server (MSCS), and on an Oracle database. Your conversion target is SAP S/4HANA 1909.
For the supported DB/OS combination, see SAP Note 2835781 first.


------------------< Update D036824 OCT/06/2020 >----------------------
-----------------------< D053440 04/MAR/2019 >--------------------------
System with SLT as source system for conversion
If the SAP ERP system that you want to convert to an SAP S/4HANA system is used as a source system by an SAP Landscape Transformation Replication Server (SLT), see SAP Note 2755741 for potential impacts of SLT during the conversion.


-------------------< Update D029945 SEP/21/18 >-----------------------
-----------------------< D019209 MAR/21/18 >--------------------------
Recommended AS Platforms for SAP S/4HANA and SAP BW/4HANA
Before your start the conversion, check SAP Note 2620910 for the recommended application server platforms for the different versions of SAP S/4HANA and SAP BW/4HANA.
If you are planning system activities on a de-supported platform (such as conversion or upgrade), see SAP Note 2696472 for more information.

----------------------< D065274 JAN/18/2017 >-------------------------
Optimize parallel execution of conversion reports
While converting an SAP system to SAP S/4HANA, existing data is converted into the new S/4HANA data model. The conversion is performed by several ABAP reports. Some of these reports will run in parallel processes to maximize the conversion throughput. Those reports come with a default setting for their parallelization parameters. To maximize the benefit of parallel processing and to minimize the technical downtime, you may need to adapt the settings to your system environment. For more information about optimizing parallel execution of conversion reports, see SAP Note 2351294.


----------------------< D028431 OCT/31/2016 >-------------------------
MM: Run migration report for T130F
The customizing table T130F is switched from table type G to E in an SAP S/4HANA system. All SAP owned entries in this table won't be changeable in a customer system without modification and customer changes originated in an SAP ERP system are overwritten with the SAP delivery settings after migration. For some fields, the deviating customer settings need to be kept and therefore, those changes need to be migrated to new customizing table via a migration report. See SAP Note 2323185 for more information.


----------------------< I318218 OCT/31/2016 >-------------------------
Implement SAP Note 2336018  to suppress mandatory Business Partner field groups
During the conversion to S/4HANA, there is a requirement to suppress mandatory field group customizing checks of Business Partner from MDS_LOAD_COCKPIT transaction which gets logged in MDS_PPO2 transaction. See SAP Note 2336018 for more information.


----------------------< I318218 OCT/31/2016 >-------------------------
Run report for S/4HANA Automation for Master Data Migration
Before you start the conversion, run a report that checks the necessary CVI and Business Partner Customizing for each client and proposes a solution for missing or wrong Customizing entries. See SAP Note 2344034 for more information.


----------------------< I065383 OCT/31/2016 >-------------------------
Run pre-check for business partner
Before you start the conversion, perform the pre-conversion check for Business Partners to ensure that all the necessary CVI Link and CVI mappings are done for both customer and vendor. See SAP Note 2216176 for more information.


-----------------------< D028310 NOV/18/15 >--------------------------
Uninstallation of ABAP add-ons
I you want to uninstall ABAP add-ons, consider SAP Note 2011192 before you start the conversion.


-----------------------< D039661 NOV/11/15 >--------------------------
Handling of SAP ERP Java instances
If you are planning a conversion of your SAP ECC server to SAP S/4HANA, and you have SAP ERP Java instances connected to the SAP ECC server via the same product system, consider SAP Note 2207818 before you start the conversion.


-----------------------< D039661 NOV/09/15 >--------------------------
Inconsistencies in link tables of master data synchronization
To prevent inconsistent data in link tables CVI_CUST_LINK, CVI_VEND_LINK, and CVI_CUST_CT_LINK, consider SAP Note 974504 before you start the conversion.


-----------------------< D039661 NOV/05/15 >--------------------------
MaxDB/liveCache 7.9.08.33 on SUN OS: Consider SAP Note 2217880
To prevent that the conversion based on MaxDB/liveCache 7.9.08.33 on SUN OS fails, consider SAP Note 2217880 before you start the conversion.

 

 

IV/ Problems During the Conversion Process
This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under very specific circumstances.

------------< Update D044220 17/JAN/22 >------------------------------
----------------< D044220 04/AUG/21 >---------------------------------
SDM aborts when the time stamps cannot be converted to a date
You perform a system conversion to SAP S/4HANA 2020 or higher. The silent data migration of the class SDMI CL_SDM_S4PPM_PROJECT_DATE_19A aborts when it converts invalid time stamps or the task timestamp 31.12.9999 to dates. The Software Update Manager stops in phase PARRUN_SILENT_DATA_MIGR with the following error message:

CL_SDM_S4PPM_PROJECT_DATE_19A client &1 finished with error on &2 at &3"

In addition, the SDMI Monitor (transaction SDM_MON) shows that the silent data migration of the class CL_SDM_S4PPM_PROJECT_DATE_19A has been canceled. For more information and a solution, see SAP Notes 3076952 and 3135114.

------------------< Update D044220 FEB/02/2022 >----------------------
----------------------< D044220 JAN/13/2022 >-------------------------
Short dump due to exception RESOURCE_FAILURE in phase MAIN_NEWBAS/PARRUN_SILENT_DATA_MIGR
During a conversion to a stack based on SAP_BASIS 756 SP00, the Software Update Manager stops with an error in phase MAIN_NEWBAS/PARRUN_SILENT_DATA_MIGR. The log file contains the following error message:

A2EEUPGBA 503 SDM stops all migrations due to system failure or CPIC failure

In addition, the ABAP system displays a short dump with the short text "Exception condition "RESOURCE_FAILURE" triggered".
For more information and to solve the error, see SAP Note 3099309 and 3112215.

-----------------------< D023536 21/JAN/2021 >--------------------------
Error in phase RUN_RWLF_WBRL_MIGRATION
If the Software Update Manager stops in phase RUN_RWLF_WBRL_MIGRATION with an error, see SAP Note 3013123 for more information.

-----------------------< D044220 19/NOV/2020 >--------------------------
SAP S/4HANA 2020: Issue in phase RUN_VBFA_MIGRATION
You are performing a system conversion from SAP ERP to SAP S/4HANA 2020, and the procedure stops in phase MAIN_NEWBAS/RUN_VBFA_MIGRATION. The logfile VBFA_MIGRATION.<SID> contains the following error message:
A4EESD_PROGRESS_LOG 006 Step "DETERMINE_DDIC_CHANGES" failed: Content missing in table "RTOBJ cannot be instanciated"
For more information and to solve the issue, see SAP Note 2993284. The issue is fixed with Feature Pack 01 of SAP S/4HANA 2020.


-----------------------< D023536 03/NOV/2020 >--------------------------
Phase XPRAS_AIMMRG fails during the execution of program RMXPRAS4SIMIGRATION
During the conversion, the phase XPRAS_AIMMRG aborts during the execution of program RMXPRAS4SIMIGRATION due to an uncaught exception.
In transaction ST22 (ABAP Dump Analysis), you can see a corresponding shortdump UNCAUGHT_EXCEPTION with context READ_TRANS_CUSTOMIZING_EXT in CL_SMT_FACTORY. For more information, see SAP Note 2986870.


-----------------------< D039661 12/AUG/2020 >--------------------------
Error in START_SHDI_PREPUT: Shadow instance cannot be started
You encounter in phase MAIN_SHDPREPUT/START_SHDI_PREPUT the error that the shadow instance cannot be started.
To solve the issue, use the SAP HANA 2.0 SP05 client with version 2.05.105 or a higher version.


-----------------------< D039661 MAY/25/2020 >--------------------------
Error with regard to PAi components
The system conversion stops with the following error message:

HANA_UMML with version <version> is not installed on the database!

The reason is that the components of the Predictive Analytics integrator (PAi) instance have been selected in the SAP Maintenance Planner, but they are not yet installed by the SAP HANA database lifecycle management tool (hdblcm). The component SAP_AFL_SDK_APL and the SAP HANA Delivery Unit HANA_UMML must already be installed in the system before you proceed. For more information, see SAP Note 2928582.


-----------------------< D039661 DEC/13/2018 >--------------------------
Deadlock while accessing table DDPRS
If you encounter a deadlock in phase MAIN_NEWBAS/XPRAS_AIMMRG due to a dump DBSQL_SQL_ERROR in ABAP Program RADBTLOG with error message "SQL code: 133" occurred while accessing table "DDPRS", see SAP Note 2728636 for more information.


-----------------------< D039661 26/OCT/2018 >--------------------------
SAP BW: Issues with ADSO during conversion
If you encounter frequent access to  "SYS"."OBJECT_DEPENDENCIES" during accessing DataTransfer Processes (DTPs) with source as Advanced DataStore Object (ADSO), and due to this you encounter performance problems, see SAP Note 2684950 for more information.

If an ADSO, which has no data, is changed where the change log was created or deleted, then the initialization of the DTP looks for the wrong tables for extraction. See SAP Note 2652045 for more information.

The installation of DTPs with source as ADSO or content upgrade leads to short dump 'ASSERTION_FAILED' in method CL_RSDSO_X_ADSO_TPL=>_DETERMINE_TABNMAES' after installing SAP Note 2652045 or upgrading to an equivalent support package. See SAP Note 2711902 for more information.

The issues are solved with SAP_BW 753 SP01.


-----------------------< D023536 11/MAY/2018 >--------------------------
Error in phase JOB_RS_DMO_HDB_CONTENT_ACTIVATE when running on SAP HANA 2.0 SP3
In case the phase JOB_RS_DMO_HDB_CONTENT_ACTIVATE fails with the following error message:

Repository: Encountered an error in repository runtime extension;Model inconsistency.
Create Scenario failed: The following errors occurred: Index does not exist;Failed to get CalcIndex
'ISP::_SYS_BIC:sap.erp.sfin.fi.gl/FAC_GLACCT_HIER_LEAF_IN_COMPANY_CODE (t -1)' (2007)

Install SAP Note 2631364 using transaction SNOTE and repeat the current phase.

-----------------------< D039661 19/JAN/2018 >--------------------------
Error messages related to POGT
During the conversion from EHP8 FOR SAP ERP 6.0 SP08 (or higher) to SAP S/4HANA, you encounter in phase ACT_UPG activation errors for certain generated DDIC objects generated by the Purchase Order Generation Tool (POGT) that uses the condition application PGT and the usage PT. Example of such a message:

3 EDT012XActivate table "/1CN/WORKING_SET_E_D_PGT"
1EEDT242 Field "FSH_POG_AUART": Component type or domain used not active or does not exist

For more information, see SAP Note 2590824.


------------------< Update D040734 JUL/16/18 >----------------------
-----------------------< D025168 JAN/17/18 >--------------------------
MAIN_NEWBAS/XPRAS_AIMMRG stops with error in XPRA MD03_XPRA_MRP_AREA_RETAIL
During the conversion, the phase MAIN_NEWBAS/XPRAS_AIMMRG stops with an error in program XPRA MD03_XPRA_MRP_AREA_RETAIL. In ST22, you can see a corresponding shortdump DBSQL_REDIRECT_INCONSISTENCY for the affected table MARD or MARC. For more information and to solve the issue, see SAP Note 2589530 if the table is MARD, or see SAP Note 2659526 if the table is MARC.


----------------------< I033682 OKT/10/2017 >-------------------------
Error in phase RUN_MFLE_XPRA_DTTABLES
During a S/4HANA DIMP LAMA conversion, you encounter the following error:

Error Batchjob RSUPG_MFLE_XPRA_PARALLEL_CALL failed
### CURRENT PHASE: RUN_MFLE_XPRA_DTTABLES
Does the downtime migration for selected MFLE tables ERRORS and RETURN CODE in MFLE_XPRA_DTTABLES.<sys id>
A3EEMFLE_TOOLS 132 Table <table name>: status not set to converted

For more information and to solve the issue, see SAP Note 2525668.

-----------------------< D039661 SEP/06/17 >--------------------------
Phase MAIN_NEWBAS/PARRUN_MIG_CV_BP_S4: System failure while starting remote function call
The Software Update Manager stops in phase MAIN_NEWBAS/PARRUN_MIG_CV_BP_S4 with an error message such as:

A4 EUPGBA 002 "Start Migration of Cust./Supplier from retail site"
A2EEWRF_UPGRADE_MSG 016 System failure while starting remote function call &4", client 001"&1" "&2" "&3" "

To solve this issue, repeat the phase MAIN_NEWBAS/PARRUN_MIG_CV_BP_S4.

-----------------------< D023536 SEP/05/17 >--------------------------
Errors in phase XPRAS_AIM for method RS_AFTER_IMPORT or UJT_AFTER_IMPORT
The following error messages might occur:

2 EPU122XPost-import method "RS_AFTER_IMPORT" started for "ASOB" "L", date and time: …

or

2 EPU122XPost-import method "UJT_AFTER_IMPORT" started for "AAPP" "L", date and time: …A2AERSO 781 Invalid objects: 'After Import' terminated (see long text)"***2"
A2AERSO 876XError "Current Import all request" "xxxxxxxx" ("SELECT internal table l_th_trkorr_import_all RC =") in TP command "4"
A2AERSO 876XError "Current imported l_th_trkorr_import_all has" "x" "lines") in TP command "Fatal error: Import all mismatch"
A2AERSO 876XError "xxxxxxxx" "xxxxxxxx" ("0000") in TP command "Returncode of trkorr trkorr_no_1".
"xxxxxxxx" stands for the names of different transport requests.

To bypass the error, execute report RS_IMPORT_ALL_BW_BUFFER_DEL  and repeat the phase XPRAS_AIMMERGE.

-----------------------< D024081 AUG/11/17 >--------------------------
S/4HANA: Database error 391
If you encounter a database error 391 in system messages during a conversion to S/4HANA, see SAP Note 2517415 for more information and to solve the issue.


-----------------------< D028733 FEB/27/17 >--------------------------
PPM: XPRA report /S4PPM/XPRA_S4MIG_PROJECT aborts with dump ITAB_DUPLICATE_KEY
During the SUM run, the XPRA program /S4PPM/XPRA_S4MIG_PROJECT aborts with a dump ITAB_DUPLICATE_KEY, which is documented in ABAP Dump Analysis (transaction ST22). To solve this issue, implement SAP Note 2426838.


-------------------< Update D025168 MAR/29/17 >----------------------
-----------------------< D040734 FEB/22/17 >--------------------------
Site master/Business Partner Harmonization: Duplicate key dump in Supplier to BP synchronization
The creation of business partners for customers/suppliers assigned to Retail sites during SAP S/4HANA conversion may fail due to a dump in saving the supplier data of the business partner in tables CVI_VEND_LINK and CVI_VEND_CT_LINK. You can find the dump DBSQL_DUPLICATE_KEY_ERROR in upgrade logs, and you see in upgrade log file MIGRATION_CV_BP the message WRF_UPGRADE_MSG 24: No migration occurred for plant &1 (customer &2, supplier &3) &4.
If you encounter this error, implement SAP Note 2429142 after the S/4HANA conversion downtime and follow the instructions given there to create the missing business partners and to complete the site conversion.


------------------< Update D024092 APR/10/17 >----------------------
-----------------------< D023536 JAN/27/17 >--------------------------
IS-OIL: No new lines found in logfiles
SUM stops in phases MAIN_NEWBAS/PARRUN_MKPF2_S4 or PARRUN_SMIG_UT_MKPF2_S4 with the following error message:

Checks after phase <phase name> were negative!
Last error code set:
No new lines found in logfiles.

In this case, implement SAP Note 2422861 to solve the issue.


-----------------------< D039661 NOV/05/15 >--------------------------
Conversion with source database SAP ASE 16.0 can fail due to SAP ASE error 8201
The conversion procedure can fail in various phases of the SUM run due to an error in the SAP ASE source database. When you analyze the log files of the Software Update Manager, you will find an error message similar to the one below:

TPERR- error in dbdd_get_size: 4
TPERR- msg: SpaceUsedForObject(OIRA_PRINTGP): Read failed (99 [[ASE Error SQL21][SAP][ASE ODBC Driver][Adaptive Server Enterprise]WARNING - Fatal Error 8201 occurred at Sep 24 2015 5:35PM. Please note the error and time, and contact a user with System Administrator (SA) authorization.

For more information and to solve this issue, see SAP Note 2233552.


-----------------------< D039661 JAN/15/16 >--------------------------
Activation errors related to A509DATA16* objects
If you encounter activation errors related to objects that begin with A509DATA16*, you can ignore these errors. This issue does not occur anymore as of SAP HR 6.08 SP24.


-----------------------< D023536 MAY/03/16 >--------------------------
Phase TP_ACTION_CP2STAB fails with error message
During the conversion, the phase TP_ACTION_CP2STAB fails with the following error message:

3 ETW685Xstart copying of "R3TRTABUDOTM_CON_ASSOC" ...
2EETW000 one entry for table DOTM_CON_ASSOC not copied - both insert and update failed.

4 ETW000  [     dev trc,00000]  statistics db_con_rollback (roll_total=0, roll_tx=0)
4 ETW000 Disconnected from database.
4 ETW000 End of Transport (0008).
4 ETW000 date&time: 16.04.2016 - 21:37:49
4 ETW000 1 error occurred.
2EETP200 Export with errors, request will not be imported

In this case, logon to the database and delete all entries from table "DOTM_CON_ASSOC~". Afterwards repeat the phase TP_ACTION_CP2STAB in the Software Update Manager.

-----------------------< D039661 NOV/05/15 >--------------------------
Error while activating switch BC set DIMP_DCGNO_T012T_S
If you encounter an error during the activation of the switch BC set DIMP_DCGNO_T012T_S in the SAP S/4HANA-system, see SAP Note 2230609 for more information and to solve this issue.


-----------------------< D039661 NOV/05/15 >--------------------------
Error while activating switch BC set DIMP_DCGNO_T399D_T
If you encounter an error during the activation of the switch BC set DIMP_DCGNO_T399_T in the SAP S/4HANA-system, see SAP Note 2239065 for more information and to solve this issue.


-----------------------< D038245 SEP/15/16 >--------------------------
Error regarding table DBPROPERTIES after reset
If you have to reset the upgrade procedure, phase EU_CLONE_MIG_DT_REV may fail with an error message regarding table DBPROPERTIES.
You can ignore the whole phase in the user interface. The schema user will later be dropped on the SAP HANA database which will clean up the remaining tables.

 

 

V/ Problems After the Conversion
This section addresses known problems that cannot be avoided using preventive measures. These problems will only occur under specific circumstances.

-----------------------< D044220 MAR/09/2021 >--------------------------
SAP S/4HANA 1909 SP00 and SP01: Enhancement objects are delivered inconsistently
After a system conversion to SAP S/4HANA 1909 SP00 or SP01, you see that some enhancement objects of technical type ENHO are missing.
We recommend to use SAP S/4HANA 1909 SP02 or a higher support package as target release.
For more information, see SAP Note 3028517.


-----------------------< D023536 SEP/02/19 >--------------------------
Shortdump DBSQL_SQL_DEADLOCK_DETECTED during XPRAS_AIMMRG
If you observe during XPRAS_AIMMRG a shortdump DBSQL_SQL_DEADLOCK_DETECTED with regard to program /1SAP1/LTR_ILTR_PIFD_DELETE while accessing table CNVMBTINTERFACE, you can ignore the error. This phase is automatically repeated by SUM, and if it stops then without errors, the deadlock situation doesn't occur anymore when the program runs a second time.

-----------------------< D026713 MAY/19/16 >--------------------------
Error with report RPCEDTD0_HRFORMS_OPTIONS
You encounter after the conversion to S/4HANA the following error: Error when generating selection screen "1000" of report "RPCEDTD0_HRFORMS_OPTIONS".
For more information and to solve this issue, see SAP Note 2316221.


-----------------------< D024643 APR/28/16 >--------------------------
Supplier Information and Master Data: Changes to maintenance view V_BUT_CALL_FU of delivery class G not considered
During a conversion to SAP S/4HANA, changes to the maintenance view V_BUT_CALL_FU of delivery class G are not taken into account. You have to deactivate those entries manually. See also SAP Note 2284393.


-----------------------< D039661 NOV/05/15 >--------------------------
Invalid log entries during running of classification table related XPRAs
During the run of XPRA reports at the classification area, log entries are reported without any issue, such as:

A2PEMFLE_TOOLS 014 No update string for object type "001", field "OBJEK" and table "AUSP" created

See SAP Note 2239779 for more information.


-----------------------< D039661 NOV/05/15 >--------------------------
DBA Cockpit: Objects in Missing Tables and Indexes that are not known in the ABAP Dictionary
In the DBA Cockpit, you see in "Diagnostics -> Missing tables and indexes" objects, displayed as errors, which exist only in the database and are not defined in the ABAP Dictionary. For more information, see SAP Note 2222905.


-----------------------< D039661 NOV/05/15 >--------------------------
Error GEN_SELECTION_SCREEN_ERROR for Reports RV13xxxx during/after Upgrade
If you encounter runtime errors of the type GEN_SELECTION_SCREEN_ERROR in reports starting with 'RV13', see SAP Note 2236577 for more information.


-----------------------< D039661 NOV/05/15 >--------------------------
Search help MCH1: Warning message DH176
During the check or activation of the search help /SAPMP/MCH1 or COWIPB_MCH1, the system issues the warning message DH176:

Parameter list of append search help /SAPMP/MCH1 (or COWIPB_MCH1) differs from appending one

For more information, see SAP Notes 2008162 or 2128083.


-----------------------< D039661 NOV/05/15 >--------------------------
DBSQL_TABLE_UNKNOWN dumps
If you are facing DBSQL_TABLE_UNKNOWN dumps caused by the FM SWNC_COLLECTOR_STARTER, apply SAP Note 2236822 to solve this issue. Such dumps are harmless so you can just ignore them.

-----------------------< D039661 NOV/05/15 >--------------------------
TABLE_KEY for old Changedocuments formatted wrongly
In function module MFLE_CHANGEDOCUMENTS_READ_ALL, old and new Changedocuments are selected and transformed into new format for displaying. However, TABLE_KEY is formatted wrong. To solve this issue, apply SAP Note 2236652.

 

***************************
Part D Chronological Summary

Date......Section....Short description
---------------------------------------------------------------------------------------
15/NOV/22...III..Target S/4HANA 2020 on Linux: Consider supported SLES and RHEL versions
08/FEB/22...III..S/4HANA 2021: Tasks cannot be released during SPDD
07/FEB/22...IV...Short dump due to exception RESOURCE_FAILURE in phase MAIN_NEWBAS/PARRUN_SILENT_DATA_MIGR
14/JAN/22...IV...SDM aborts when the time stamps cannot be converted to a date
09/MAR/21...V....SAP S/4HANA 1909 SP00 and SP01: Enhancement objects are delivered inconsistently
03/FEB/21...I....SUM creates shadow repository on target database
21/JAN/21...IV...Error in phase RUN_RWLF_WBRL_MIGRATION
19/NOV/20...IV...SAP S/4HANA 2020: Issue in phase RUN_VBFA_MIGRATION
03/NOV/20...IV...Phase XPRAS_AIMMRG fails during the execution of program RMXPRAS4SIMIGRATION
06/OCT/20...III..System with SLT as source system for conversion
12/AUG/20...IV...Error in START_SHDI_PREPUT: Shadow instance cannot be started
25/MAY/20...IV...Error with regard to PAi components
20/MAR/20...B....Supported start releases
17/SEP/19...III..Oracle on SAP system with MSCS Cluster: Check DB/OS combination for conversion to SAP S/4HANA 1909
02/SEP/19...V....Shortdump DBSQL_SQL_DEADLOCK_DETECTED during XPRAS_AIMMRG
29/APR/19...IV...Oil&GAS: DDIC_TYPE_INCONSISTENCY dumps during phase XPRAS_SHD_AIMMERGE
13/DEC/18...IV...Deadlock while accessing table DDPRS
26/OCT/18...IV...SAP BW: Issues with ADSO during conversion
21/SEP/18...III..Recommended AS Platforms for SAP S/4HANA and SAP BW/4HANA
16/JUL/18...IV...MAIN_NEWBAS/XPRAS_AIMMRG stops with error in XPRA MD03_XPRA_MRP_AREA_RETAIL
11/MAY/18...IV...Error in phase JOB_RS_DMO_HDB_CONTENT_ACTIVATE when running on SAP HANA 2.0 SP3
19/JAN/18...IV...Error messages related to POGT
10/OCT/17...IV...Error in phase RUN_MFLE_XPRA_DTTABLES
06/SEP/17...IV...Phase MAIN_NEWBAS/PARRUN_MIG_CV_BP_S4: System failure while starting remote function call
05/SEP/17...IV...Errors in phase XPRAS_AIM for method RS_AFTER_IMPORT or UJT_AFTER_IMPORT
11/AUG/17...IV...S/4HANA: Database error 391
10/APR/17...IV...IS-OIL: No new lines found in logfiles
29/MAR/17...IV...Site master/Business Partner Harmonization: Duplicate key dump in Vendor to BP synchronization
27/FEB/17...IV...PPM: XPRA report /S4PPM/XPRA_S4MIG_PROJECT aborts with dump ITAB_DUPLICATE_KEY
18/JAN/17...III..Optimize parallel execution of conversion reports
31/OCT/16...III..MM: Run migration report for T130F
31/OCT/16...III..Implement SAP Note 2336018  to suppress mandatory Business Partner field groups
31/OCT/16...III..Run report for S/4HANA Automation for Master Data Migration
31/OCT/16...III..Run pre-check for business partner
15/SEP/16...IV...Error regarding table DBPROPERTIES after reset
19/MAY/16...V....Error with report RPCEDTD0_HRFORMS_OPTIONS
03/MAY/16...IV...Phase TP_ACTION_CP2STAB fails with error message
28/APR/16...I....DVDs not required anymore, archives are calculated automatically
28/APR/16...V....Supplier Information and Master Data: Changes to maintenance view V_BUT_CALL_FU of delivery class G not considered
15/JAN/16...IV...Activation errors related to A509DATA16* objects
18/NOV/15...III..Uninstallation of ABAP add-ons
11/NOV/15...III..Handling of SAP ERP Java instances
09/NOV/15...III..Inconsistencies in link tables of master data synchronization
05/NOV/15...III..MaxDB/liveCache 7.9.08.33 on SUN OS: Consider SAP Note 2217880
05/NOV/15...V....DBA Cockpit: Objects in Missing tables and Indexes that are not known in the ABAP Dictionary
05/NOV/15...V....Error GEN_SELECTION_SCREEN_ERROR for Reports RV13xxxx during/after Upgrade
05/NOV/15...V....Search help MCH1: Warning message DH176
05/NOV/15...V....DBSQL_TABLE_UNKNOWN dumps
05/NOV/15...V....TABLE_KEY for old Changedocuments formatted wrongly
05/NOV/15...IV...Error while activating switch BC set DIMP_DCGNO_T012T_S
05/NOV/15...V....Invalid log entries during running of classification table related XPRAs
05/NOV/15...IV...Conversion based on SAP ASE 16.0 can fail due to ASE error 8201